home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20020314-20021006
/
000246_fdc@columbia.edu_Mon Jul 29 11:43:45 EDT 2002.msg
< prev
next >
Wrap
Text File
|
2002-10-06
|
2KB
|
67 lines
Article: 13560 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!news.columbia.edu!news-not-for-mail
From: fdc@columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Help needed in setup of Host - dialin client
Date: 29 Jul 2002 11:43:38 -0400
Organization: Columbia University
Lines: 50
Message-ID: <ai3nra$gg0$1@watsol.cc.columbia.edu>
References: <71dc564d.0207261309.7bfa937a@posting.google.com> <ahse5j$6uc$1@watsol.cc.columbia.edu> <71dc564d.0207290729.32a9d6cb@posting.google.com>
NNTP-Posting-Host: watsol.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1027957420 28835 128.59.39.139 (29 Jul 2002 15:43:40 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 29 Jul 2002 15:43:40 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:13560
In article <71dc564d.0207290729.32a9d6cb@posting.google.com>,
chuck <greg180@aol.com> wrote:
: ...
: Thanks for simplifing my problem, less IS indeed more.
:
: Further, Chapter 11 is my new best friend. I had
: not Read The Fine Manual to that point.
:
: It seems my problem is on the client side now.
: Some subtle point or set command I am missing?
: Further elaboration seems to be needed...
:
: On the host side call, is answered, the server reports itself
: present and displays the messages below (I set server display off)
:
: Speed changed to 26400
: Call complete: "CONNECT 26400".
: Entering server mode on Boca V90 Tidalwave External FD
: Type Ctrl-C to quit.
:
: --------------
: Client seems unable to talk to the server however
:
: After I dial it connects, and I Alt-X to command screen.
: I issue an RDIR (to test the connection) and I receive the message
:
: Press X or E key to cancel.
:
: E of course cancels, X errors out after 60+ seconds.
:
: When I quit the client session, host sees it as well
: and sets up for next call as hoped.
:
The call is answered, the connection is made, but no useful communication
is happening. Usually this is explained by one of the basic serial
communication parameters discussed in Chapter 3:
. Interface speed
. Flow control
. Parity
It's almost certainly not parity. My guess is interface speed:
: Speed changed to 26400
: Call complete: "CONNECT 26400".
Try adding "set modem speed-matching off" to your script.
Also make sure both sends have RTS/CTS flow control.
- Frank